@robert-hh Thanks for that information robert.

@paul-thornton Sad that everyone needs to have a subscription model... and an expensive one!

@einarj said in Expansion board 3.0 power consumption: @crumble Your initial answer was using the Pycoproc together with the expansion board 3? Yes. You came back with i2c problems. The Pycoproc is used by pysense and pytrack as well. All 3 boards use the PIC for handling firmware update, deepsleep and so on. But there is a chance to run into this i2c problem - depending on firmware version and your hard-/software setup.

@curtis-hendrix I have no spec but I once tried to connect a small LCD display to that power pin. That was an instructive failiure. Even 400 mA is optimistic (may only be reachable at the limit of 5.5 V Gpy supply). You can safely use that 3.3 V pin to supply some I²C chips but nothing that needs power.

@spiderplant0 Hi, I can't speak to the specifics of your case--I'm using a bare GPy sitting on a custom board--but I've also been looking into deep sleep current consumption. I started a thread on the GPy board, where you can see my tests and results, but the short version is that with all the networks/peripherals down and doing a machine.deepsleep() the best I've gotten is also around the 0.5mA mark. This is a total guess, but it looks very similar to doing a deepsleep() rather than actually "pulling the plug" as that shield seems to allow for.

@tanmay07 Got it thanks a ton! I was also looking for another scenario where I do not have to use this. Suppose I configure my device to be on a deepsleep it consumes about 25uA current. But I want it to wake up on certain levels of voltage from my sensors on analog pins. Is it possible to do this using:- machine.pin_deepsleep_wakeup(pins, mode, enable_pull) ?? Because I believe this function can only wakeup the decice from deep sleep if the specidied pins goes high or low.This can be used for specific voltage levels on analog pins right?